Mirror Giraffe

At least that means you’re good at avoiding tech dept!

Where I work we use mongo, it’s not what I would’ve picked but i guess it helped early dev speed and bad practices like having productus do direct db edits to save a situation because the app isn’t mature yet.

By now when collections are getting huge and documents as well we’ve had to archive more and more recent data, which causes problems, and we have to really make sure our queries are sharp or cost and lag will go through the roof.

With that said, it actually works pretty ok for a production platform with quite a big customer base, and there are many improvements we could do if we had the time.

If I were there at day one I’d have rooted for sql, mainly based on how much these different collections have to relate, but I don’t think mongo is as horrible as many people make it out to be and it does have upsides.

Imo each test tests a specific functionality which requires a fixture set up for that. Its important that these figures mirror exactly how it would look in production or the tests are pointless.

For example customer A uses product A in a specific way it’s important that we enter customerA.settings and productA.props into the test and only test the specifics in said transaction.

I didn’t finish it, but where I got to there were no real power ups you needed to progress the game, more find ways to sneak around the map.

It’s a beautiful game indeed and definitely touches the genre at least.

Companies that foster their juniors to first learn to solve problems on their own and then learn to use these tools to increase their output in a safe and efficient manner will most likely triumph over companies that seek to run an ai code farm.

It can help out a lot in writing base systems. I wanted to learn rust and made gpt write a game with me, it really could handle more complex things than I thought. For example it wrote a diablo style rotatable inventory system (cli, no graphic) which impressed me a lot.

Another game prototype i had lying around in react i asked Jules to refactor to use event sourcing rather than mutating values and I only had to give it a few pointers on what it had missed. It even found an old bug I had missed.

I guess nothing of it was really math heavy but that inventory grid was really solid

I’m vegan and it’s my diet!

One thing that’s common when having multiple sources like different data sources, cms and utility services is having a backend for frontend (BFF) which is what your frontend would call and in turn it would gather all your resources and format it the way your frontend expects it. The bff can cache the more static sources while proxying more dynamic ones.

This might be overkill for your project but it’s a nice paradigm when you’re dealing with multiple sources or sources that might change.

Don’t worry, we’ll refactor when we get time!

I’ve ended up becoming the sole caretaker of two react native apps, something I did not ask for but some people were fried.

I’m not going to manually troubleshoot and learn everything that breaks when I need to update a dependency. I’ll vibe through those errors, learn what I have time for and then test it like mad.

A lot of the time I end up having to solve things myself but my job wouldn’t be tolerable if I had to manually work that shit.

I use insomnia but many of the updates to it disrupt my workflow. I should probably find something else.

Been looking for a spiritual successor for 25 years but nothing scratches that itch.

With that said the game is widely unbalanced and full of totally broken strategies, which somehow doesn’t make it less fun.

I’m a big fan of supermaven as well. The speed really is what sold it to me, I don’t wait for it but rather check out it’s suggestions as I type.